Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Log files

A log file contains log message header information and log message content. The message content is set by the log entry type and the logging level. Log entry types are described in the "Log entry types" section. Logging levels are described in the "Logging levels" section.

The message header information is consistent across all combinations of log entry types and logging levels. For example:

[06/10/31@14:07:15.892-0400] P-002702 T-002867 2 4GL DYNOBJECTS

Where:

06/10/31 is the date in yy/mm/dd format.
14:07:15.892 is the time in hh:mm:ss.mls.
0400 is the time zone, expressed as the number of hours relative to GMT.
002702 is the process ID.
002867 is the thread ID.
2 is the logging level associated with this log entry.
4GL is the execution environment.
DYNOBJECTS is the log entry type.

For a 4GL client, specify the log file with the Client Logging (-clientlog) startup parameter. For AppServer and WebSpeed, the log is the normal AppServer or WebSpeed log file (for example, asbroker1.server.log). For WebSpeed Messenger, Unified Broker, NameServer, AIA, the log file is specified through Progress Explorer.